Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.7 updates #50

Merged
merged 1 commit into from
Dec 19, 2017
Merged

0.7 updates #50

merged 1 commit into from
Dec 19, 2017

Conversation

quinnj
Copy link
Collaborator

@quinnj quinnj commented Dec 18, 2017

No description provided.

@omus
Copy link

omus commented Dec 18, 2017

Why not just wait for Compat.Unicode?

@quinnj
Copy link
Collaborator Author

quinnj commented Dec 18, 2017

Because these are super trivial uses and this package doesn't rely on Compat currently anyway.

@quinnj quinnj merged commit ec6bffe into master Dec 19, 2017
@quinnj quinnj deleted the jq/0.7 branch December 19, 2017 03:50
@@ -3,7 +3,7 @@ export Dec32, Dec64, Dec128, @d_str, @d32_str, @d64_str, @d128_str

const libbid = joinpath(dirname(@__FILE__), "..", "deps", "libbid$(Sys.WORD_SIZE)")

const _buffer = Vector{UInt8}(1024)
const _buffer = fill(0x00, 1024)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, we can no longer allocate uninitialized arrays in 0.7?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can, it would be like Vector{UInt8}(uninitialized, 1024), I just prefer the terseness of fill now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants